|
CAN Kingdom is a communications protocol running on top of CAN. It is designed as a fieldbus. Unlike other CAN high level protocols, it makes no attempt to follow the OSI model. The network is mostly distributed, as the nodes may run autonomously except that a "King" or master controller is needed to configure the network. A major design philosophy behind CAN Kingdom is that the system designer is fully aware of the capabilities of the nodes. A node designer, on the other hand, needs to know nothing about the other nodes: a node merely provides services to the network, and it is up to the system designer to activate a node's services or not through runtime configuration. The specification〔() CAN Kingdom specification rev.3.01〕 is freely available. ==Terminology== In order to make network terminology friendly to non systems designers, CAN Kingdom uses lay-friendly names. *Page : a CAN data payload *Envelope : a CAN identifier *Letter : a CAN frame *Form : a specification for fixed format data presented in a page *Document : a set of forms or pages (depending on context) *Folder : maps a single document to a set of envelopes *City/Mayor : a node and its controller *Capital/King : the single master controlling node *City Founder : the (human) module designer *Kingdom Founder : the (human) network designer 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「CAN Kingdom」の詳細全文を読む スポンサード リンク
|